Skip to content

Chore: [AEA-0000] - use gitleaks for secret scanning#17

Merged
anthony-nhs merged 2 commits intomainfrom
gitleaks
Apr 17, 2026
Merged

Chore: [AEA-0000] - use gitleaks for secret scanning#17
anthony-nhs merged 2 commits intomainfrom
gitleaks

Conversation

@anthony-nhs
Copy link
Copy Markdown
Contributor

use gitleaks for secret scanning

Copilot AI review requested due to automatic review settings April 17, 2026 10:44
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the repository’s pre-commit setup to improve local security checks, aligning with the goal of using gitleaks for secret scanning.

Changes:

  • Add a local grype-scan-local pre-commit hook that runs via make.
  • Fix the gitleaks hook id (gitleasksgitleaks) and consolidate its description formatting.
Comments suppressed due to low confidence (1)

.pre-commit-config.yaml:96

  • The gitleaks hook description claims it scans commit messages and --no-ff merges, but this pre-commit config only runs at the pre-commit stage (default_stages: [ pre-commit ]). Either adjust the description to match what actually runs here, or explicitly configure stages (e.g., include commit-msg/other relevant stages) so the behavior matches the description.
        name: Git Leaks
        description: gitleaks scans commits, commit messages, and --no-ff merges to prevent adding secrets into your git repositories.
        entry: bash
        args:
          - -c
          - "gitleaks git --pre-commit --redact --staged --verbose"
        language: system

@anthony-nhs anthony-nhs merged commit f2be05f into main Apr 17, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants